BABY is initiated when one parent process polls another server process through a socket connection (BSD) or, in the System V implementation, through pipes.
BABY runs at a low priority for approximately 40 weeks, then terminates with a heavy system load. Most systems require constant monitoring when BABY reaches its final stages of execution.
Older implementations of BABY required that the initiating process not be present at the time of completion. In these versions, the initiating process is awakened and notified of the results upon completion. Modern versions allow both parent processes to be active during the final stages of BABY.
The SLEEP command may not work on either parent process for sometime afterward, as new BABY processes constantly send interrupts that must be handled by one or more parents.
BABY processes, upon being created, may frequently dump in /tmp, requiring /tmp to be cleaned out frequently by one of the parent processes.
The original AT&T version was provided without instructions regarding the created process; this remains in current implementation.
^C (quit process) is deemed illegal in certain countries, check with local authorities.